• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The present invention relates to a distributed SCADA (supervisory control and building automation) system for building automation monitoring. In this SCADA system, the SCADA functionality is distributed in the system so that each part of the system functions independently, and at the same time is possible to be monitored as one system.For publication: Figure 2.
    公开号:SE1551038A1
    申请号:SE1551038
    申请日:2015-07-24
    公开日:2017-01-25
    发明作者:Ranstorp Thomas
    申请人:Ivago Ab；
    IPC主号:
    专利说明:

    SCADA SYSTEM FOR BUILDINGS Technical fieldThe present invention relates to a distributed SCADA (supervisory control and data acquisition) system for building automation monitoring,and in particular to a SCADA system where SCADA functionality isdistributed in the system so that each part of the system functionsindependently, and at the same time is possible to be monitored as onesystem.
    BackgroundSeveral system architectures for building automation are known in the prior art.
    Building automation comprises monitoring and control. Controlfunctions are performed by computers, regulating for example the heatingsystems, cooling systems, ventilation systems and lighting systems ofbuilding. l/lonitoring functions allow staff to manage control functions. Thisis performed through user interfaces that for example visualize themonitoring functions through dynamic flow charts, store data forvisualizing historical trends, and handle alarm signals.
    Generally, a central computer communicates with control systemsand with computers responsible for parts of the system. An example ofsuch architectures is SCADA/PLC. ln general, while being highlyconfigurable, these systems are somewhat difficult and labor-intensive toset up. Furthermore, these systems are difficult to maintain and toreconfigure, for example if a system is to be split due to the sale of abuilding. Thus there is a need to provide a building automation system thatis easy to reconfigure.
    Summaryln view of the above, an objective of the invention is to solve or at least reduce one or several of the drawbacks discussed above. Generally, the above objective is achieved by the attached independent patentclaims.
    According to a first aspect, the present invention is realized by aSCADA (supervisory control and data acquisition) system comprising aplurality of separate building automation units, said plurality of separatebuilding automation units forming a tree structure wherein each separatedbuilding automation unit corresponds to a node in said tree structure. ln the context of the present specification, SCADA functionalitycomprises the monitoring and control of building automation functions,such as heating systems, cooling systems, ventilation systems andlighting systems. ln particular, it comprises the monitoring and control ofone or more signals arising from such functions. Furthermore, it comprisesthe visualization of the interdependence of such signals through dynamicflow charts, the storing and/or visualization of historical signal data, andthe handling of alarms arising from the behavior of such signals.
    The plurality of separate building automation units forms a logicaltree structure, wherein each unit may be associated with zero, one, ormore child units, each child unit being one of said plurality of separatebuilding automation units. ln this specification, a “building automation unit”(or just “unit”) and a “node” will be used as terms for the same feature, i.e.for a building automation unit in the tree structure. Each buildingautomation unit comprises zero or more pieces of address information,where each piece of address information pertains to the address in thenetwork of one child unit of the building automation unit.
    Each building automation unit is connected to a network and has anaddress in that network. lt is separate in the sense that it provides a fullSCADA system for SCADA functionality handled by the buildingautomation unit or by its child units. ln the context of the present specification, a building automationunit may be implemented in a PLC, or in a gateway acting as an interfacebetween the SCADA system according to the invention and legacybuilding automation systems. A building automation unit may also beimplemented in software in a personal computer. l/loreover, a building automation unit may be implemented in e.g. HVAC (heating, ventilating,and air Conditioning) devices such as air handling units, chillers, fan coils,pump devices etc. One or more of these building automation units may becontained within one physical device. ln other words, a PLC may containseveral building automation units.
    Furthermore, each building automation unit is configured to handleSCADA functionality of said SCADA system. A building automation uniteither directly performs the SCADA functionality (e.g. when implementedin the device itself) or communicates with equipment performing thatfunctionality.
    Furthermore, each building automation unit comprises a userinterface, UI, controller for displaying information relating to SCADAfunctionality of the SCADA system. The UI controller may be used by anoperator of the SCADA system for displaying graphical data relating toSCADA functionality of the SCADA system, trend graphs relating to dataof SCAD functionality, alarm lists etc.
    Since each building automation unit comprises its own UI controller,a provider of such building automation unit may brand a displayed UIrelating to the building automation unit as desired.
    Each building automation unit is configured to receive a request, viathe network, for pieces of address information and transmit suchinformation in response thereto.
    Each building automation unit is configured to receive a request, viasaid network, for said UI controller and in response thereto transmit, viasaid network, said UI controller.
    Each building automation unit is configured to receive a request, viasaid network, for data relating to SCADA functionality handled by said unit,and in response thereto transmit, via said network, transmit said data.
    An advantage hereof is that information on SCADA functionality isdistributed in the system so that each part of the system functionsindependently. The logical tree structure may be navigated by requestingaddress information from the building automation units so that informationon all SCADA functionality of a building automation unit, being a node in the Iogical tree structure and its child units (child nodes in the Iogical treestructure) may be acquired, so that the system is easily monitored andcontrolled. Information on the relationship between the buildingautomation units is kept in the system in a distributed fashion.Furthermore, building automation units may be easily added or removedfrom the system. A system is easily set up from existing buildingautomation units. An existing system may easily be split up. Adding orremoving parts of the system requires no reconfiguration. SCADAfunctionality handled by a building automation unit may be used andaccessed at any level of the system. Since each building automation unitcomprises its own UI controller, an operator with access to the SCADAsystem may connect to any part of the tree structure (i.e. to any node) andstill be able to display data relating to the SCADA functionality handled bysaid unit. By traversing the tree structure, i.e. the children and theirchildren etc., of the node to which the operator connected, data relating tothe SCADA functionality handled by all of the nodes of the tree may bedisplayed. Furthermore, since a UI controller is arranged to displayinformation relating to SCADA functionality of the SCADA system, a singleUI controller (branded as desired) may be utilized to display data relatingto all nodes of the tree. This will be further described below.
    A UI controller may be implemented in javascript or any othersuitable programming language.
    Each separate building automation unit may further comprisemetadata pertaining to the SCADA functionality handled by that buildingautomation unit. ln the context of the present specification, metadatacomprises descriptive information on one or more signals pertaining to theSCADA functionality, such as the name of a signal, the available ofhistorical data for a signal, or the available of dynamic flow charts for oneor more signals. The metadata may further comprise the names of thechild nodes and other meta data relating to the child nodes. Each buildingautomation unit is configured to receive a request, via the network, for metadata, and to respond thereto by transmitting the requested metadata.
    An advantage hereof is that the metadata can be accessed withoutactually asking for the data for data relating to SCADA functionalityhandled by said unit, or without actually traversing the tree structure to findinformation about the number of child nodes of a node.
    Each separate unit may further be configured to receive a request,via the network, to add a further piece of address information, where thatfurther piece of address information pertains to an address in the networkof a second separate building automation unit. The second separatebuilding automation unit is thereby being associated as a child unit to theseparate building automation unit in the tree structure when its addressinformation is added as a further piece of address information.
    An advantage hereof is that new building automation units mayeasily be added to the system. All that is required is the address in thenetwork to the child unit to be added. No further information or request isneeded in order to add a child unit to the tree structure. The child unit mayhave child units added itself, with those units becoming grandchildren ofthe original building automation unit. A first existing tree structure ofbuilding automation units may be added to a second existing tree structureby adding the top node, or top building automation unit, of the first tree toa suitable structure unit of the second tree. All this may be done withoutreconfiguring the SCADA functionality of any of the building automationunits, giving high flexibility in the configuration of the system. For example,a new building acquired by a landlord may easily be added to the system.By utilizing the UI controller as discussed above, data relating to SCADAfunctionality of the newly added tree structure or building automationnodes may be directly visualized and controlled.
    Each separate building automation unit may further be configuredto receive a request, via the network, to remove a piece of addressinformation, where that further piece of address information pertains to theaddress in the network of a third separate unit. The third separate unit isthereby being removed as a child unit to the separate building automationunit in the tree structure when its address information is removed from thepieces of address information.
    An advantage hereof is that a unit and its child units may easily beremoved from the system while SCADA functionality handled by thosebuilding automation units continues to function just as before. As noreconfiguring is needed, work time is saved. For example, a building soldoff by a landlord may easily be removed from the system while SCADAfunctionality pertaining to that building continues to function just as before.A mother building automation unit (i.e. top node) of that building may thenbe added to another tree structure containing building automation units inthe buildings owned by the new owner.
    The SCADA functionality may comprise the handling historicalvalues. By storing historical signal values in the building automation unitsin a distributed fashion, those values may be used and accessed at anylevel of the system, while still allowing the system to be easily split up. Thehistorical values for SCADA functionality relating to a specific buildingautomation unit may be included in the data relating to SCADAfunctionality which the specific automation unit can transmit when askedfor.
    The SCADA functionality may comprise at least one from the list of:signal data, alarm signals, alarm texts, alarm priorities and dynamic flowcharts. These may also be included in the data relating to SCADAfunctionality which the specific automation unit can transmit when askedfor.
    A UI controller of any of the building automation units in the SCADAsystem may be arranged to use said data relating to SCADA functionalityfor displaying graphical representation of said SCADA functionality. Byhaving this functionality in the units in a distributed fashion, those valuesmay be used and accessed at any level of the system, while still allowingthe system to be easily split up or reconfigured.
    A UI controller of a specific building automation unit may beconfigured to traverse the tree structure of the building automaton unitswhich are descendent to the specific building automation unit in the treestructure by requesting pieces of address information. A descendent ofany specific building automation unit is any building automation unit which is either the child of the specific building automation unit or is (recursively)the descendent of any of the children of the specific building automationunit.
    An advantage hereof is no information on SCADA functionalityneeds to be stored in a centralized database.
    According to some embodiments, the SCADA system furtherimplementing a user interface, said user interface being controlled by userinterface controller received from a building automation unit correspondingto a top node in said tree structure, said user interface controller beingconfigured to communicate with each of the plurality of buildingautomation units using said network, said user interface presenting saiddata relating SCADA functionality.
    By utilizing the UI controller of the top node in the tree structure fordisplaying data relating to SCADA functionality of the SCADA system inthe user interface, branding of the SCADA system is easily handled. Forexample, if the top node relates to a shopping mall named “l/lALL”, theuser interface may be branded “l/lALL” even when presenting data relatingto a specific air handling unit (handled by a building automation unit beinga descendent to the top node) in a room of the mall. According to anotherexample, the top node relates to a chiller from the vendor “CHILLERZ inthat case, the user interface may be branded “CHILLEFV even whenpresenting data relating to a fan coil (handled by a building automationunit being a descendent to the top node, which may be manufactured bya vendor “FAN COIL”) of the chiller.
    The user interface may be configured to present a single alarm list,comprising alarms from all handlers of all units.
    The user interface may be web based.
    The user interface may further allow the addition or removal of achild unit at any level of said tree structure by sending a request to aparent unit of said child unit. An advantage hereof is that the tree structuremay be managed from the same user interface as is used for SCADAfunctionality.
    The user interface controller may be configured so that said userinterface may be accessed through a single-sign-on procedure. Anadvantage hereof is that a seamless user interface may be presentedwhile keeping the distributed nature of the system.
    Brief description of the drawinqs These and other aspects of the invention will now be described inmore detail, with reference to one embodiment of the invention.
    Fig. 1 shows an overview of the system, including the tree structureof the units.
    Fig. 2 is a schematic drawing of the architecture of a SCADAsystem according to embodiments.
    Fig. 3 shows a configuration where a unit may be part of more thanone system.
    Fig. 4 shows a procedure where data is loaded as a user interactswith the user interface.
    Fig. 5 schematically shows an example user interface.
    Detailed descriptionThe present disclosure concerns architecture for building a SCADA (supervisory control and data acquisition) system for buildings. ln thecontext of the present specification, SCADA functionality comprises themonitoring and control of building automation functions, such as heatingsystems, cooling systems, ventilation systems and lighting systems. lnparticular, it comprises the monitoring and control of one or more signalsarising from such functions. Furthermore, it may comprise the visualizationof the interdependence of such signals through dynamic flow charts, thestoring and/or visualization of historical signal data, and the handling ofalarms arising from the behavior of such signals.Functions for monitoring and control are placed locally in the units, i.e., in a distributed fashion. Each part of the system functionsindependently. At the same time, a user interface presenting all parts ofthe system is presented to the user. SCADA functionality handled by a building automating unit may be used and accessed at any level of thesystem.
    A system may comprise several sub-systems, each sub-systemfunctioning autonomously. Sub-systems may be linked or aggregatedtogether hierarchically without being integrated, since data and informationare stored in a distributed fashion. The user experiences a single system.The higher up in the hierarchy one connects to, the larger the system ispresented. A UI displaying the system and data relating to SCADAfunctionality of the system may be branded according to where in thehierarchy the connection takes place. Each sub-system may itself haveother sub-systems and may be part of several aggregated SCADAsystems, for example one used by a landlord and one used by acaretaker.
    Sub-systems are handled by separate building automation units,where each building automation unit is separate in the sense that itprovides a full SCADA system for SCADA functionality handled by thebuilding automation unit or by its child units. Child units of a unit handlinga (sub-)system themselves handle sub-systems.
    Fig. 1 shows the tree structure of one embodiment of the SCADAsystem. The system comprises units 1, 12, 13, 14, 15 and a user interfacecontroller 17, all connected to a network 3. ln the example shown fiveunits 1, 12, 13, 14, 15 are present. Their logical relationship in the treestructure is shown using dashed lines. The parent unit 1 has a first childunit 12 and a second child unit 13. The second child unit 12 has itself afirst 14 and a second 15 child unit, which become grandchildren to theparent unit 1. Each building automation unit 1, 12, 13, 14, 15 is configuredto handle SCADA functionality of said SCADA system (cf. Fig 2). Eachbuilding automation unit 1, 12-15 comprises a UI controller. ln figure 1,only the UI controller 17 of the parent building automation unit 1 is shown.A user may connect to the user interface controller 17 using a personalcomputer 19 and a user interface (i.e. web browser) 25, wherein thecomputer 19 is connected to the network 3. ln one embodiment, the user accesses the user interface through asingle sign on procedure so that the entire system is accessible for theuser using the UI 25 of the computer 19.
    A building automation unit may be a physical device, such as a PLCunit, but there may also be several building automation units within onephysical device.
    Each unit 1, 12, 13, 14, 15 further stores metadata pertaining to theSCADA functionality handled by that unit. ln the context of the presentspecification, metadata comprises descriptive information on one or moresignals, such as the name of a signal, the available of historical data for asignal, or the available of dynamic flow charts for one or more signals.Each unit is configured to receive a request, via the network, for metadata,and to respond thereto by transmitting the requested metadata. ln one embodiment the user interface controller 17 is connected toa web server (e.g. implemented in the building automation unit) to which auser may connect using a web browser 25 running on the personalcomputer 19. The user is presented with the user interface 25 (see alsoFig. 2 and Fig. 5). The UI controller 17 may be implemented using one orseveral of the following technologies: HTl/lL5, CSS, Javascript, Java, orSVG graphics.
    The user interface controller 17 traverses the logical tree structureof the units 1, 12, 13, 14, 15, requesting pieces address information fromthe units. lt may further request for data relating to SCADA functionalityhandled by the units of the tree structure, and present a single alarm listpertaining to alarms from all handlers of all building automation units 1, 12,13, 14, 15. Furthermore the user interface is configured to display the treestructure in the user interface. The user interface allows a user to addand/or remove units from the logical tree structure. The logical treestructure may be navigated by requesting address information from theunits 1, 12, 13, 14, 15. lnformation on SCADA functionality (data relating to SCADAfunctionality) may be exchanged and/or stored in one or several of thefollowing formats: JSON, Xl/IL, text files. 11 Fig. 2 shows the architecture of parts of the SCADA system offigure 1 according to embodiments. By way of example, the parentbuilding automation unit 1 and one of its child building automation units 13(cf. Fig. 1) are shown.
    The building automation unit 1 comprises a UI controller 17 fordisplaying information relating to SCADA functionality of the SCADAsystem. When connecting to the SCADA systems, the web browser startsby requesting, via the network (reference 3 in figure 1), for the UIcontroller 17. ln response thereto, the building automation unit 1 transmit,via said network, said UI controller 17. This means that the Web browser25 is displaying the UI controller 17, which may be implemented injavascript.
    The building automation unit 1 comprises zero or more pieces ofaddress information 24, each piece of address information pertaining tothe address of one of said child units of said separate unit. ln this case,the address information 24 comprises the address to the child buildingautomation unit 13. The building automation unit 1 is configured to receivea request 200, via the network, the request 200 sent out by the webbrowser 25 via the UI controller 17, for at least one of said zero or morepieces of address information 24, and in response thereto transmit 200,via said network, information pertaining to said at least one of said zero ormore pieces of address information.
    Now the Web browser 25 may display a tree structure comprisingthe parent node 1 and the child node 13. ln case the operator of the web browser wants to display datarelating to SCADA functionality handled by the parent building automationunit 1, the building automation unit 1 is configured to receive a request202, via said network, for data relating to SCADA functionality handled bysaid unit, and in response thereto transmit 202, via said network, saiddata. The data handling of a building automation unit may be implementedusing separate functionality 26-28 in the building automation unit 1.
    For example, a signal data handling functionality 26 may beimplemented, which comprises the handling of historical values of the 12 SCADA functionality handled by the building automation unit. Such datacan be used for displaying trends regarding the SCADA functionality at theweb browser 25. For example, trends for heating from a radiator.
    According to other examples, an alarm handling functionality 27may be implemented. The UI controller 17 may be configured for bothdisplaying data relating to alarms, using the data transmitted 202 by thealarm handling functionality 27, and/or it can be implemented to turn offthe alarm, acknowledge the alarm etc.
    According to other examples, graphics functionality 28 may beimplemented. The graphics functionality 28 may be implemented todisplay dynamic flow charts relating to SCADA functionality, as will bedescribed further in conjunction with figure 5 below.
    The child unit 13 (the relationship to the parent unit 1 illustrated bythe arrow 210) comprises the same functionality as the parent unit 1. lnother words, the child unit is configured to receive a request 208, via saidnetwork, for data relating to SCADA functionality handled by said unit 13,and in response thereto transmit 208, via said network, said data. Thedata handling of the building automation unit 13 may be implementedusing separate functionality 34-26 as described above for the parent unit1.
    The building automation unit 13 also comprises zero or more piecesof address information 32, each piece of address information pertaining tothe address of one of said child units of said separate unit. ln this case,the address information 24 comprises zero pieces of address information32. Anyhow, the building automation unit 1 is configured to receive arequest 206, via the network, from the UI controller 17 of the web browser25, for at least one of said zero or more pieces of address information 24,and in response thereto transmit 200, via said network, informationpertaining to said at least one of said zero or more pieces of addressinformation. ln this case, the transmitted 206 information will contain nodata indicating that no child unit exists, and the UI displayed to theoperator will display no child units to the building automation unit 13. 13 The building automation unit 13 also comprises a UI controller 31.ln case the operator of the Web browser 25 chooses to connect to thechild unit 13, the UI controller 31 will be utilized by the web browser inorder to display information about the SCADA system.
    Child units of the building automation units may added or removedby changing the stored peaces 24, 32 of address information. Each unit 1itself has its own address in the network 3. ln one embodiment, thenetwork is IP (lnternet Protocol) based and each piece 24, 32 of addressinformation is an IP address.
    Each building automation unit 1, 13 further comprises metadata 30,33 pertaining to SCADA functionality handled by the building automationunit 1, 13 associated with that unit. According to the embodiment shown infigure 2, such metadata accessed in the same way as the addressinformation is accessed. According to some embodiments, the addressinformation and the metadata are accessed by the web browser 25 andthe UI controller 17 by requesting 200, 206 a description object from thebuilding automation units 1, 13, wherein the description object comprisesboth the address information of any child nodes, and the metadata 30, 33pertaining to SCADA functionality.
    Furthermore, the unit may be requested over the network to add anew child unit to its list 24, 32 of address information.
    Furthermore, the unit may be requested over the network to removea child unit from its list 24, 32 of address information.
    Fig. 3 shows schematically a configuration where a unit may be partof more than one system. ln the example shown, a first owner A owns twobuildings a and b, while a second owner B owns two different buildings cand d. A building automation unit 21 is a parent building automation unitfor building automation units 23, 25 serving, respectively, buildings a andb, while another building automation unit is the 27 is the parent buildingautomation unit for building automation units 29, 31 serving, respectivelybuildings c and d. The building automation units 23, 25, 29, 31 servingeach building may themselves have child units (not shown). Owner Ausing his corresponding building automation unit 21 will have access to 14 the building automation units serving the buildings owned by him, whileowner B till have access to the buildings owned by him using hiscorresponding building automation unit 27. At the same time a caretakerC, contracted by owners A and B for managing, respectively buildings aand d will through a building automation unit 33 have access to buildingautomation units 23 and 31, corresponding to the buildings placed underhis care. An advantage of this architecture is that no reconfiguration ofSCADA functionality is needed as different use cases are added.
    Fig. 4 shows illustrates a procedure as a user accesses SCADAfunctionality though the user interface. First 401, a user connects to a userinterface controller 17 (cf. Fig 1) of the parent node of the tree structure,by signing on to the building automation unit corresponding to the parentnode. l/letadata on SCADA functionality handled locally by a parent unit isloaded, including links to child units of that parent unit (e.g. the request200 in figure 2). lf the user selects 403 a child unit, metadata on SCADAfunctionality handled by that child unit is requested (request 206 in figure2) from that child unit, using the pieces of address information 24 retrievedfrom the parent unit. lf the user selects 405 a dynamic flow chart handledby the child unit, the dynamic flow chart is retrieved 406 (request 208 infigure 2) from that child unit.
    Fig. 5 schematically shows a user interface in one embodiment.The user interface comprises a toolbar 35, a data area 37, a tree view 49and an alarm list 39.
    The toolbar 35 comprises one or more clickable icons, allowing, forexample the selection of dynamic flow charts, graphs of historical data, oralarm lists to be shown in the data area 37.
    The tree view 39 presents the logical tree structure of the units 1,12, 13, 14, 15 (cf. Fig 1) to the user. ln the example shown, a parent unithas one child unit, marked as Child, which itself has one child unit, markedas G.child. The parent unit has two associated pictures marked as Pict1,Pict2. The child unit has two associated pictures marked as Pict3 andPict4. Finally the, grandchild unit has three associated pictures, marked asPict5, Pict6, and Pict7. The tree view 39 is populated by traversing the logical tree structure, and for each building automation unit (node in thetree structure) asking for the address information in order to furthertraverse the tree structure. I/|oreover, for each building automation unit,any metadata present in the building automation unit is used to populatethe tree view 39 with e.g. names of the pictures. The pictures may bedynamic flow charts. The user may select a picture to be shown in thedata area 37 by clicking on it in the tree view. The user may interact withthe tree view 39 to add or remove units from the system. ln the example shown, the data area 37 shows a dynamic flowchart 43 which shows current values of a number of signals, for examplethe picture marked as Pict6 in the tree view 39. This information isretrieved by requesting for data relating to SCADA functionality handled bythe building automation unit marked as G.child in the tree view 39. ln thiscase, the data is transmitted from the graphics functionality of the G.childunit as a dynamic flow chart (dynamic P&ID) which the user can interact.ln this example, two signals 45, 47 are shown. A first signal gives thestatus of a pump though the color of symbol 45. lf the symbol 45 is green(not shown) the pump is running, while if the symbol 45 is red (not shown),the pump is not running. The user may control the pump by clicking on itscorresponding symbol. The graphical signal 47 gives a reading from atemperature sensor.
    The alarm list 41 may be used by to show prioritized alarms,marked Alarm1 and Alarm2 at all times. Alarms shown are aggregatedfrom all units 1, 12, 13, 14, 15 (cf. Fig 1) in the system.
    The present disclosure is not limited by the above example, andmay be varied and altered in different way within the scope of theappended claims.
    权利要求:
    Claims (13)
    [1] 1. A SCADA (supervisory control and data acquisition) system comprisinga plurality of separate building automation units, said plurality of separatebuilding automation units forming a tree structure wherein each separatedbuilding automation unit corresponds to a node in said tree structure;each separate building automation unit of said plurality of separatebuilding automation units:being connected to a network;having an address in said network;being associated with zero or more child units in said treestructure; andconfigured to handle SCADA functionality of said SCADAsystem;each separate building automation unit of said plurality of separatebuilding automation units comprising:zero or more pieces of address information, each piece ofaddress information pertaining to the address of one of said child unitsof said separate building automation unit; anda user interface, UI, controller for displaying information relatingto SCADA functionality of the SCADA system,each separate unit of said plurality of separate units being configuredto:receive a request, via said network, for at least one of said zeroor more pieces of address information, and in response theretotransmit, via said network, information pertaining to said at least one ofsaid zero or more pieces of address information;receive a request, via said network, for said UI controller and inresponse thereto transmit, via said network, said UI controller; andreceive a request, via said network, for data relating to SCADAfunctionality handled by said unit, and in response thereto transmit, viasaid network, said data. 17
    [2] 2. The SCADA system according to claim 1, wherein each separatebuilding automation unit further comprises metadata pertaining to saidSCADA functionality handled by said building automation unit, wherein eachseparate building automation unit of said plurality of separate buildingautomation units is configured to receive a request, via said network, for saidmetadata, and in response thereto transmit, via said network, said metadata.
    [3] 3. The SCADA system according to any one of the claims 1-2, eachseparate building automation unit further being configured to receive arequest, via said network, to add a further piece of address information, saidfurther piece of address information pertaining to an address in said networkof a second separate building automation unit, and in response to saidrequest, add said further piece of address information to the zero or morepieces of address information, wherein said second separate buildingautomation unit thereby is associated as a child unit to said separate buildingautomation unit in said tree structure.
    [4] 4. The SCADA system according to any one of the claims 1-3, eachseparate building automation unit further being configured to receive arequest, via said network, to remove a piece of address information, saidfurther piece of address information pertaining to an address in said networkof a third separate building automation unit, and in response to said request,remove said piece of address information from the zero or more pieces ofaddress information, said third separate building automation unit therebybeing removed as a child unit to said separate building automation unit in saidtree structure.
    [5] 5. The SCADA system according to any one of the claims 1-4, whereinsaid SCADA functionality comprises the handling of historical values.
    [6] 6. The SCADA system according to any one of the claims 1-5, whereinsaid SCADA functionality comprises at least one from the list of: signal data,alarm signals, alarm texts, alarm priorities and dynamic flow charts. 18
    [7] 7. The SCADA system according to any one of the claims 1-6, wherein aUI controller is arranged to use said data relating to SCADA functionality fordisplaying graphical representation of said SCADA functionality.
    [8] 8. The SCADA system according to any one of the claims 1-7, saidSCADA system further implementing a user interface, said user interfacebeing controlled by user interface controller received from a buildingautomation unit corresponding to a top node in said tree structure, said userinterface controller being configured to communicate with each of the pluralityof building automation units using said network, said user interface presentingsaid data relating SCADA functionality.
    [9] 9. The SCADA system according to claim 8, said user interface controllerbeing configured to traverse said tree structure of said separate units byrequesting said pieces of address from said plurality of building automation units.
    [10] 10. The SCADA system according to any one of the claims 8-9, said userinterface being configured to present a single alarm list, comprising alarmsfrom all of said plurality of separate building automation units.
    [11] 11. The SCADA system according to any one of the claims 8-10, whereinsaid user interface is web based.
    [12] 12. The SCADA system according to any one of the claims 8-11, said userinterface further allowing the addition or removal of a child units at any level ofsaid tree structure by sending a request to a parent unit of said child unit.
    [13] 13. The SCADA system according to any one of the claims 1-12, said userinterface controller being configured to traverse said tree structure of saidseparate units through a single-sign-on procedure.
    类似技术:
    公开号 | 公开日 | 专利标题
    CA2886591C|2021-01-12|System for monitoring multiple building automation systems
    CN109219783A|2019-01-15|Building management system with automatic equipment discovery and device model distribution
    US10728053B2|2020-07-28|System and method for remote monitoring and controlling of building automation devices
    EP3644557B1|2021-05-05|Scalable visualization of health data for network devices
    CN106506213B|2019-11-05|A kind of internet of things equipment visualization interface display methods and system
    US20160291826A1|2016-10-06|STANDALONE AND DISTRIBUTED APPLICATION FOR SIMULATION OF INTERNET OF THINGS | SCENARIOS
    US10790999B2|2020-09-29|Connected machines automation platform with intuitive network configuration and deployment management interface
    JP2015138544A|2015-07-30|Method and system for monitoring control variable of multivariable prediction controller in industrial plant
    US10096138B2|2018-10-09|Control map providing method and apparatus
    JPH11109933A|1999-04-23|Monitoring and controlling system
    SE1551038A1|2017-01-25|Scada system for buildings
    US20160127310A1|2016-05-05|Distributedindustrial control monitoring and management
    KR20160042668A|2016-04-20|Central control apparatus for controlling facilities and operation method thereof
    JP4300149B2|2009-07-22|Field monitoring system, field monitoring method and field monitoring program
    JP2014026437A|2014-02-06|Information collection system, server device, and information collection method
    US20200182498A1|2020-06-11|Extracting and publishing point data from a building site model
    KR20090033197A|2009-04-01|Intergrating control multiplex network device for variety 3rd party serial communication device
    Farinha et al.2014|CMMS–An integrated view from maintenance management to on-line condition monitoring
    JP2019008690A|2019-01-17|Gateway apparatus, data access method executed by gateway apparatus, controller, and data access method executed by controller
    JP6793881B1|2020-12-02|Management equipment, management system, management method and program
    KR20190142644A|2019-12-27|Method for controlling weight value of control map and apparatus thereof
    US20190005155A1|2019-01-03|Visualization management device, data management device, data visualization system, visualization management method, and program product
    Vinogradov et al.2022|Architecture of Distributed Sensor System for Automated Greenhouse Complex
    Yu et al.2016|A dynamic and interactive monitoring system of data center resources
    CN113934241A|2022-01-14|SDN-based machine room temperature adjusting method and device
    同族专利:
    公开号 | 公开日
    SE540156C2|2018-04-17|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    法律状态:
    优先权:
    申请号 | 申请日 | 专利标题
    SE1551038A|SE540156C2|2015-07-24|2015-07-24|Scada system for buildings|SE1551038A| SE540156C2|2015-07-24|2015-07-24|Scada system for buildings|
    [返回顶部]